Frame relay switched data service

ABSTRACT

A new type of data transport service which uses a frame relay layer  2  data link connection identifier (DLCI) to select among various service types, feature sets, and/or closed user groups (CUGs). A layer  3  address may be extracted from a layer  2  frame, and the layer  3  address information may be used to route a data packet over a packet-switched network according to the service classes, feature sets, and/or CUGs selected. At the destination, the layer  3  data packet may again be enclosed in a layer  2  frame with a DLCI indicating the service classes, features sets, and/or CUGs. Because the use of conventional permanent virtual circuits (PVCs) is not required in aspects of the invention, new methods of measuring and managing network traffic are presented.

CROSS-REFERENCES TO RELATED APPLICATIONS

The present application is a continuation of copending U.S. patentapplication Ser. No. 10/375,256 filed on Feb. 28, 2003, which is acontinuation of U.S. patent application Ser. No. 09/551,399, filed onApr. 17, 2000, which is a continuation of U.S. patent application Ser.No. 08/988,159, which is now U.S. Pat. No. 6,081,524, filed on Dec. 10,1997 and claims priority back to provisional U.S. patent applicationSer. No. 60/051,564 entitled FRAME RELAY SWITCHED DATA SERVICE, filed onJul. 3, 1997 and is related by subject matter to U.S. Patent applicationSer. No. 11/019,330, filed on Dec. 21, 2004 entitled TRAFFIC MANAGEMENTFOR FRAME RELAY SWITCHED DATA SERVICES, which is a continuation of U.S.patent application Ser. No. 09/654,616, which is now U.S. Pat. No.6,847,611, filed on Sep. 1, 2000 entitled TRAFFIC MANAGEMENT FOR FRAMERELAY SWITCHED DATA SERVICES, which is a Continuation of U.S. patentapplication Ser. No. 08/988,424, which is now U.S. Pat. No. 6,188,671,filed on Dec. 10, 1997 entitled TRAFFIC MANAGEMENT FOR FRAME RELAYSWITCHED DATA SERVICES, by the same inventors, wherein each of the aboveapplications is herein incorporated by reference.

BACKGROUND OF THE INVENTION

1. Technical Field

The present invention is directed to systems and methods forimplementing improved network architectures, and more specifically tosystems and methods for routing internet protocol (IP) packets usingmodified frame relay protocols.

2. Description of the Related Arts

Recently, the popularity of large meshed networks has been increasing.However, large-scale highly-meshed networks can be difficult toimplement, maintain, and manage using conventional network technologies.

An example of a conventional mesh configuration is shown in FIG. 1. Awide-area network (WAN) 900 includes a plurality of routers R_(A),R_(B), R_(C), R_(D), (customer premises equipment (CPE)) respectivelydisposed at a plurality of end user locations A, B, C, and D andinterconnected to a service providers network (SPN) 901 via respectiveuser-network interfaces (UNI) 920-1, -2, . . . , -n. The user-networkinterfaces 920 may be variously configured to be, for example, anasynchronous transfer mode (ATM) switch having a frame relay interfaceto CPE. Connecting the sites together are logical paths called, forexample, permanent virtual circuits (PVCs) P_(A-C), P_(A-D), P_(B-D),P_(A-B), P_(C-B), that are characterized by their endpoints at the UNIs920-1, 920-2, . . . , 920-n and a guaranteed bandwidth called thecommitted information rate (CIR).

FIG. 2 provides a detailed view of the flow of data across the WAN 900.There exists a plurality of layers of protocol over which communicationsmay occur. For example, the well-known layers of the InternationalStandards Organizations (ISO) Open Systems Interconnect Model havinglayers from a physical layer (layer 1), a datalink layer (layer 2), anetwork layer (layer 4), up through and including an application layer(layer 7). Under this model, user data 902 is generated by a userapplication running at the application layer 903. At the transport layer(layer 4) 904, a source and destination port address 906 (as part of theTCP header (layer 4)) may be added to the user data 902. At the networklayer (layer 3) 905, an additional header (i.e., an IP header (layer 3))containing source and destination IP addresses) 908 may be added. Thus,the layer 3 user data field includes the layer 4 user data 902 plus thelayer 4 header 906. The layer 3 protocol data unit (PDU) 902, 906, 908,which makes up, for example, an IP packet 950, is then passed down tolayer 2 909 in the CPE (routers R_(A), R_(B), R_(C), R_(D)) thatinterfaces to the SPN 901. In the router, a table maps one or more IPaddresses (layer 3) 908 to an appropriate PVC or PVCs (P_(A-C), P_(A-D),P_(B-D), P_(A-B), P_(C-B)). The router table is maintained by thecustomer. Once the correct PVC is located in the routing table, thecorresponding data link connection identifier (DLCI) (layer 2) 912 iscoded into the header of the frame relay frame 914 (packet). Thereafter,the remainder of the frame relay frame is included and a frame check sum(FCS) is computed. The frame is then passed down to the physical layerand transmitted to the SPN 901.

At the UNI 920, the frame is checked for validity to determine if thereis a predefined PVC associated with the DLCI 912. If so, the frame 914is then forwarded on that PVC through the network along the same pathand in the same order as other frames with that DLCI, as depicted inFIG. 2. The layer 2 frame information remains as the packet traversesthe frame relay network whether this network is actually implemented asa frame relay network or other network such as an ATM network. The frameis carried to its destination without any further routing decisionsbeing made in the network. The FCS is checked at the egress UNI, and ifthe frame is not corrupted, it is then output to the UNI associated withthe end user.

As is well known in the art, FIGS. 1-3 provide exemplary diagrams of howthe frame relay data packets are assembled at the various ISO layersusing the example of TCP/IP protocol transport over a frame relay datalink layer. The example shows how the user data at the application layeris wrapped in succeeding envelopes, making up the PDUs, as it passesdown the protocol stack. Specifically, the composition of the Headerfield is expanded for detail and is shown in FIG. 5. The data linkconnection identifier (DLCI) field comprises 10 bits spread over thefirst and second octet, and allows for 1023 possible addresses, of whichsome are reserved for specific uses by the standards. As shown in FIG.3, the DLCI is added to the frame relay header according to whatdestination IP address is specified in the IP packet. This decisionabout what DLCI is chosen is made by the CPE, usually a router, based onconfiguration information provided by the customer that provides amapping of IP addresses into the PVCs that connect the current locationwith others across the WAN 900.

In conventional frame relay, a layer 2 Q.922 frame carries the layer 3customer data packet across the network in a permanent virtual circuit(PVC) which is identified by a data link connection identifier (DLCI).Thus, the DLCIs are used by the customer as addresses that select theproper PVC to carry the data to the desired destination. The customerdata packet is carried across the network transparently and its contentsis never examined by the network.

The conventional meshed frame relay network discussed above has a numberof limitations. For example, every time a new end user location is addedto the meshed network, a new connection is required to be added to everyother end user location. Consequently, all of the routing tables must beupdated at every end user location. Thus, a ripple effect propagatesacross the entire network whenever there is a change in the networktopology. For large networks with thousands of end user locations, thisripple effect creates a large burden on both the network provider tosupply enough permanent virtual circuits (PVCs) and on the networkcustomers in updating all of their routing tables. Further, most routersare limited to peering with a maximum of 10 other routers which makesthis network topology difficult to implement. As networks grow in size,the number of PVCs customers need to manage and map to DLCIs increases.Further complicating the problem is a trend toward increasing meshednessof networks, meaning more sites are directly connected to each other.The result is a growth in the number and mesh of PVCs in networks thatdoes not scale well with current network technologies.

A possible solution for handling large meshed networks is to use avirtual private network (VPN) which interconnects end user locationsusing encrypted traffic sent via tunneling over the internet. However,VPNs are not widely supported by internet service providers (ISPs), haveerratic information rates, and present a number of security concerns.

Another possible solution is the use of frame relay based switchedvirtual circuits (SVCs). While PVCs (discussed above) are usuallydefined on a subscription basis and are analogous to leased lines, SVCsare temporary, defined on an as-needed basis, and are analogous totelephone calls. However, SVCs require continuous communications betweenall routers in the system to coordinate the SVCs. Further, because thetables mapping IP addresses to SVC addresses are typically manuallymaintained, SVCs are often impractical for large highly-meshed networks.Security is a major concern for SVC networks where tables are mismanagedor the network is spoofed. Further, frame SVCs are difficult tointerwork with asynchronous transfer mode (ATM) SVCs.

None of the above solutions adequately address the growing demand forlarge mesh networks. Accordingly, there is a need for networkarchitectures which enable implementation of large mesh networks havingsecurity, low maintenance costs, efficient operations, and scalability.

SUMMARY OF THE INVENTION

Aspects of the present invention solve one or more of the above-statedproblems and/or provide improved systems and methods for implementing anetwork architecture.

A new type of data transport service takes advantage of the existingbase of frame relay customer premises equipment (CPE) and customerswhile offering a new mechanism for providing extensible service featuresto those customers. In the new service, data link connection identifiers(DLCIs) may be used by the CPE to select among service types, featuresets, and closed user groups (CUGs). The DLCI is used in the layer 2frame that conveys the user data to the network. The layer 3 user datapacket is extracted from the layer 2 frame and the layer 3 addressinformation for the (routable) protocol is used to route the user datapacket over a high-performance packet switched network, according to theservice class/feature set selected by the DLCI. At the destination, thelayer 3 data packet is again enclosed in a layer 2 frame with a DLCIthat indicates to which service group it belongs. The frame is thenforwarded to the CPE. Use of this technique will allow the existingframe relay CPE to support, over the same physical interface,conventional frame relay service with a range of DLCIs that are linkedto logical paths such as permanent virtual circuit (PVCs), as well as arange of DLCIs that are linked to service and/or feature sets. This willallow a robust method for extension of new services to the frame relayinstalled base, with minimal impact to existing customer equipment.

In some aspects of the invention, frame relay DLCIs are used forselecting among various service categories. This differs significantlyfrom conventional frame relay, which uses DLCIs only to select PVCsand/or switched virtual circuits (SVCs). Service categories may include,but are not limited to, communication via the public internet,communication via a local intranet, communication within a closed usergroup (CUG), communication with an extranet (e.g., a network of trustedsuppliers or corporate trading partners), live audio/video transmission,multicasting, telephony over internet protocol (IP), or any combinationthereof. Thus, the concept of a frame relay PVC is significantlyexpanded by aspects of the present invention. For example, the locationof an intended network endpoint recipient is not necessarily determinedby a DLCI at a sending network endpoint. The DLCI may represent aservice category with the intended recipient indicated by an IP addresswithin the frame relay packet. This results in a significant benefit tonetwork customers because, unlike that of conventional frame relay,customers no longer need to update their local DLCI tables each time anetwork customer with whom they wish to communicate is added or removedfrom the network. Thus, the customer's burden of network administrationis substantially reduced.

In sub-aspects of the invention, some DLCIs may be used to select amongservice categories (service category DLCIs) while in the same networkother DLCIs may be used to select conventional PVCs and/or SVCs(conventional DLCIs). In other words, conventional frame relay may bemixed with aspects of the present invention within the same network,allowing aspects of the present invention to be incrementallyimplemented in existing conventional frame relay networks.

In further aspects of the invention, addressing contained in multiplelayers (e.g., as defined by the Open System Interconnection model) arecompared with each other in a network to determine routing errors. Ifthe addressing in the layers are consistent with each other, then theassociated data is routed without interruption. On the other hand, ifthe addressing in the layers is inconsistent with each other, theassociated data may be specially handled. For example, the data may bediscarded, sent to a pre-determined address, and/or returned to thesender. This address comparison may be applied to the sending addressand/or the destination address. An advantage of this multiple layeraddress comparison is that network security is increased. For instance,problems such as spoofing, which is the practice of purposely providingan incorrect sending internet protocol (IP) address, are bettercontrolled by such a method.

In still further aspects of the invention, routing look-up tables withinthe network are separated such that, for example, each customer, closeduser group (CUG), extranet, and/or intranet may have its own privatepartition and/or separate table. This can provide greater network speedbecause a router need not scan the entire available address space forall network customers at once. Furthermore, data security is improvedbecause the risk of sending data to a wrong recipient is reduced.

In yet further aspects of the invention, layer 3 and/or layer 4 IPaddress information is utilized to route the fast packets through thenetwork.

In even further aspects of the invention, new network traffic managementtechniques and measurements are defined. For example, in sometraffic-management aspects of the invention, committed delivery rates(CDRs) may be assigned to one or more UNIs. A CDR is the average minimumdata rate that is guaranteed to be delivered to a given UNI whensufficient traffic is being sent to the UNI. In furthertraffic-management aspects of the invention, a destination rate share(DRS) is assigned to one or more UNIs. The DRS may be used to determinethe share of traffic that a given UNI may send through the network. Ifseveral UNIs are simultaneously offering to send traffic to the samedestination UNI, then each sending UNIs share of the network may bedetermined by its own DRS and the DRSs of the other sending UNIs.

These and other features of the invention will be apparent uponconsideration of the following detailed description of preferredembodiments. Although the invention has been defined using the appendedclaims, these claims are exemplary in that the invention is intended toinclude the elements and steps described herein in any combination orsubcombination. Accordingly, there are any number of alternativecombinations for defining the invention, which incorporate one or moreelements from the specification, including the description, claims, anddrawings, in various combinations or subcombinations. It will beapparent to those skilled in network theory and design, in light of thepresent specification, that alternate combinations of aspects of theinvention, either alone or in combination with one or more elements orsteps defined herein, may be utilized as modifications or alterations ofthe invention or as part of the invention. It is intended that thewritten description of the invention contained herein covers all suchmodifications and alterations.

BRIEF DESCRIPTION OF THE DRAWINGS

The foregoing summary of the invention, as well as the followingdetailed description of preferred embodiments, is better understood whenread in conjunction with the accompanying drawings. For the purpose ofillustration, embodiments showing one or more aspects of the inventionare shown in the drawings. These exemplary embodiments, however, are notintended to limit the invention solely thereto.

FIG. 1 illustrates a wide area network (WAN) having routers as CPEs andPVCs between customer locations.

FIG. 2 shows data flow through the WAN shown in FIG. 1.

FIGS. 3-5 show the construction and flow of data packets through thenetwork.

FIG. 6 shows a block diagram of a network architecture in accordancewith aspects of the present invention.

FIG. 7 shows a detailed block diagram of the network illustrated in FIG.6.

FIG. 8A-8B shows a migration path for incorporating aspects of theinvention into conventional network architectures.

FIG. 9 shows data flow through the network architecture of FIG. 6.

FIG. 10 shows application based prioritization through the networkarchitecture of FIG. 6.

FIG. 11 illustrates an exemplary embodiment of a means to apportionservices through the network of FIG. 6.

FIGS. 12-14 illustrate data flow through exemplary WANs 1.

DETAILED DESCRIPTION OF PREFERRED EMBODIMENTS

Exemplary embodiments of the present invention allow the large installedbase of frame relay customer premises equipment (CPE) to be maintainedby using the same interface in a different way to deliver new sets ofservices and features to the customer. For example, the data linkconnection identifier (DLCI) known from the frame relay protocol may beused to select among several virtual private networks with differingaddress spaces, feature sets, and/or conventional permanent virtualcircuits (PVCs).

Referring to FIG. 7, a block diagram of a wide area network (WAN) 1incorporating aspects of the present invention is shown. The WAN 1includes a plurality of customer premise equipment (CPE) system, forexample routers located at each of the end user locations andinterconnected via one or more service providers networks (SPNs) 500.The SPN 500 is typically connected to a plurality of endpoint routers919 via a plurality of corresponding user network interfaces (UNIs) 402and/or one or more internet protocol (IP) switches 502. The IP switches502, UNIs 402, and/or routers/switches 501 may be interconnected so asto form a meshed network (e.g., a partial or fully meshed network).Additionally, the wide area network (WAN) 1 may contain any number of IPswitches 502 located within the WAN 1 such that it is not connecteddirectly to any endpoint routers 919, and/or one or more IP switches 502may be located at an interface between the SPN 500 and an endpointrouter 919. In further embodiments of the invention, there may bemultiple endpoint routers 919 associated with a UNI 402/IP switch 502and/or multiple UNIs 402/IP switches 502 associated with an endpointrouter 919.

The network architecture of the WAN 1 allows the number of IP switchesto increase as customers are transitioned to the new service. Forexample, as shown in FIG. 8A, initially there may be only a small number(e.g., one, two, three, etc.) of IP switches installed in the system.Where only a small number of IP switches are included in the network,traffic originating from non-IP enabled UNIs 402 (e.g., UNI A) may berouted to an IP switch 502 elsewhere in the network. Although thiscreates some negligible inefficiencies in backtracking it nonethelessallows a migration path to the new network architecture withoutsimultaneously replacing all routers 501. However, as more and moreusers are transitioned to the new network architecture of WAN 1, moreand more IP switches can be added (FIG. 8B) to accommodate the increasedload. In many embodiments, it may be desirable to eventually converteach UNI 402 to an IP switch 502 such that IP routing may beaccomplished at the edge of the network.

In some embodiments, the WAN 1 may include a combination of conventionalnetwork switches and/or routers 501 in addition to IP switches 502. Onthe other hand, every switch in the SPN 500 may be an IP switch 502.Alternatively, the WAN 1 may contain only a single IP switch 502. The IPswitches 502 may be variously configured to include a suitablemulti-layer routing switch such as a Tag Switch from Cisco. Multi layerrouting switches may also be utilized from vendors such as Ipsilon,Toshiba, IBM, and/or Telecom. IP switches are currently being developedto replace endpoint routers so that customer premise equipment (e.g.,Ethernet local area network (LAN) equipment) can connect directly to anasynchronous transfer mode (ATM) network. Aspects of the presentinvention propose using IP switches in a different manner to maintainthe huge installed base of customer premise equipment while avoiding thelimitations of previous systems. Accordingly, the IP switches inaccordance with embodiments of the invention are disposed within the SPN500 and modified to provide suitable routing and interface functions.

In some embodiments of the invention, an IP switch 502 acts as amulti-layer switch. For example, an IP switch 502 may receive ATM cells,switching some or all of the ATM cells based upon the content of IPpackets encapsulated within the ATM cells. Thus, IP addressing may beused by an IP switch 502 to determine an ATM virtual path for sendingATM cells to a destination UNI 402. In further embodiments of theinvention, higher layer addressing (e.g., transmission control program(TCP) logical ports at layer 4) may also be used by an IP switch 502 asa basis for switching ATM cells to provide a path through the SPN 500.In still further embodiments of the invention, an IP switch 502 uses IPaddresses and/or TCP logical ports to make quality of service (QOS)decisions.

In further embodiments of the invention, an endpoint router 919 mayencapsulate one or more IP packets in frame relay frame 914. In thisevent, the frame relay frames may be transmitted between an endpointrouter 919 and a corresponding UNI 402 and/or IP switch 502. Theendpoint router 919 encapsulates IP packets 950 with frame relay frames914. Further, the endpoint router 919 may set the DLCI of each framerelay frame 914 according to a particular service category (if a servicecategory DLCI is used) that the user has selected. For example, thevarious service categories may include the public internet,communication via a local intranet, communication within a closed usergroup (CUG), communication with an extranet (e.g., a network of trustedsuppliers or corporate trading partners), live audio/video transmission,multicasting, telephony over internet protocol (IP), or any combinationthereof. Thus, the concept of a frame relay PVC is significantlyexpanded by aspects of the present invention. For example, the locationof an intended network endpoint recipient is not necessarily determinedby a DLCI at the endpoint routers 919.

In further embodiments of the invention, a UNI 402 may receive framerelay frames 914 from an endpoint router 919 and divides andencapsulates frame relay frames into, for example, smaller fixed-lengthATM cells. The UNI 402 may further translates the frame relay DLCI intoan ATM address (e.g., a virtual path identifier/virtual channelidentifier (VPI/VCI)). There are various methods which may be used totranslate DLCIs to VPI/VCIs. For example, the Network InterworkingStandard as defined in Implementation Agreement #5 of the Frame RelayForum, and/or the Service Interworking Standard as defined inImplementation Agreement #8 of the Frame Relay Forum may be utilized. AnATM address associated with a service category DLCIs defines an ATMvirtual path via network routers to an IP switch 502. Thus, ATM dataassociated with a service category DLCI is ultimately sent to an IPswitch 502. However, ATM data associated with a conventional DLCI may ormay not be sent to an IP switch 502 and may be routed through thenetwork without passing through an IP switch 502. Thus, both translatedIP data and conventional PVC data may be present in the SPN 500 and/orWAN 1.

In further embodiments of the invention, a UNI 402 and/or a networkrouter 501 may send data to a predetermined IP switch 502. In evenfurther embodiments of the invention, a UNI 402 and/or a network router501 selects which IP switch 502 to send data to based upon an algorithm(e.g., based on network traffic flows, the relative distance/location ofan IP switch 502, the type of data being sent, and/or the servicecategory selected). In still further embodiments of the invention, a UNI402, network router 501, and/or IP switch 502 may send the same data tomore than one UNI 402, network router 501, and/or IP switch 502,depending upon, for example, a service category or categories.

In further embodiments of the invention, a UNI 402, an IP switch 502,and/or a network router 501 compares an ATM VPI/VCI 303-305 address withan IP address for the same data. If the two addresses are inconsistent,then the ATM cell may be discarded, sent to a pre-determined address,and/or returned to the sending location. In even further embodiments ofthe invention, layers above the layer 3 IP layer may be used for addressand/or service class generation/discrimination. For example layer 4 ofthe ISO addressing scheme and/or other application level data may beutilized to determine particular service classes.

Referring specifically to FIG. 9, the path of user data flowing throughan exemplary WAN 1 is shown. As in the frame relay case, user data atthe application layer and layer 4 requires the addition of a layer 3network address header. In the CPE a decision is made based oninformation in layers 3 and 4 about which virtual private network (VPN),service class, or conventional PVC the packet should be routed to. Thus,a packet with layer 4 information indicating it is a telnet(interactive) application and layer 3 information that it is an internalcompany address might go to VPN A for a low-delay intranet class ofservice. Another packet that is part of a file transfer protocol (FTP)file transfer might go to VPN B with a lower service class, and a thirdpacket going between two heavily utilized applications might go on adedicated PVC D. These decisions are coded as different DLCI values,inserted in the layer 2 frame, and sent into the UNI.

At the UNI A 402, the switching based on the DLCI takes place. Thepacket may be routed to IP switch 502 in the center of the SPN 500. Thefirst packet has its layer 2 frame stripped off as it is forwarded toVPN A. Within VPN A, the layer 3 address is now used to make routingdecisions that send the packet to its destination UNI. Thus, no PVC needbe established ahead of time for that path, and conventional routingmethods and protocols can be used, as well as newer short-cut routingtechniques. This permits VPN A to provide a high mesh of connectivitybetween sites without requiring the customer to configure and maintainthe mesh as a large number of PVCs. The packet forwarded to VPN B istreated similarly except that VPN B is implemented with a lower serviceclass (e.g. higher delay). Finally, the packet forwarded to PVC D hasits layer 2 frame intact and passes through the network as aconventional frame relay frame. This allows customers to maintain theircurrent connectivity of PVCs for their high utilization traffic paths,but still have a high mesh of connectivity through various VPNs.

Thus, in various aspects of the invention, the WAN 1 and/or SPN 500 maybe any suitable fast packet network receiving frame relay data packetshaving user data in a user data field. The WAN 1 and/or SPN 500 thenswitches packets using one or more IP switches 502 responsive to theuser data. The user data may be used to discriminate between a pluralityof different service categories based on the user data. Routing over theWAN 1 and/or SPN 500 may be responsive to at least one of the differentservice categories including discriminating based on multicast data.Additionally, the WAN may generate a fast packet address fieldresponsive to the IP packet data and route the IP packet through thefast packet network responsive to the fast packet address field.Further, layer 4 information may be utilized to determine the quality ofservice. The quality of service may include, for example, one or more ofthe following: an information rate, priority information, delay, loss,availability, etc. Security features may be implemented in the IP switchsuch that routing tables for each of the users are separated based onone or more service categories and/or users. In this manner the systemis made more secure. Still further, the system may receive a pluralityof frame relay packets over a permanent virtual circuit (PVC) at a firstnode in an asynchronous transfer mode (ATM) network, generate an ATMaddress based on a data field other than a data link connectionidentifier (DLCI) within the frame relay packets, and then route thepackets through the ATM network based on the ATM address. The routing ofpackets may be responsive to one of a plurality of service categories.The system may provide separate routing tables within an ATM switch foreach of a plurality of different service categories. The differentservice categories may be determined using internet protocol (IP) datawithin a data field of a packet passed by the ATM switch. In a fastpacket network, a fast packet switch may compare an address of a fastpacket with a layer 3 internet protocol (IP) address contained withinthe fast packet and determining whether the fast packet address isconsistent with the layer 3 IP address. Further, for security, hardwarecircuits and/or software may be provided for examination of a sendingaddress or a destination address. Further, packets may be discardedresponsive to an inconsistency being detected. The WAN 1 may includecustomer premises equipment (CPE) and an asynchronous transfer mode(ATM) switch coupled to and receiving from the CPE frame relay datapackets, and including address translation circuitry for translatingdata link connection identifiers from the frame relay data packets intoATM addresses representing a plurality of virtual private networks basedon a predetermined service category associated with a particular DLCI;or the WAN 1 may include customer premises equipment (CPE) and a fastpacket switch coupled to the CPE via one or more permanent virtualcircuits and receiving frame relay data packets, the fast packet switchincluding address translation circuitry for translating user data withinthe frame relay data packets into fast packet addresses.

In embodiments of the present invention, data security is enhanced inthat data may be easily and accurately checked for inconsistencies atthe destination. This is because these embodiments operate using bothlayer 2 and layer 3 addressing information. As an illustration, assumethat a frame relay frame having a DLCI indicating VPN 1 (e.g., thecorporate intranet) arrives in a network switch/router with an IPaddress of a particular corporate accounting system. However, since theVPN processor has available to it the DLCI of the packet (and thusinformation about the source of the packet), the VPN processor maycross-check the DLCI with the source IP address in the packet to see ifthe source IP address is in the range known from the originating site.Thus, the problem associated with the spoofing of IP source addressesmay be significantly reduced.

In still further embodiments of the invention, a UNI 402, an IP switch502, and/or a network router 501 has separate and/or partitioned routinglook-up tables. Routing tables may be separated based upon servicecategory, customer or user, and/or UNI 402. Thus, in some embodiments,within a VPN, a customer or user may have an individual routing tablecontaining the customers IP network address information. In someembodiments, since the DLCI identifies the source of a frame, the DLCImay be used as an index by an IP switch, network router, and/or UNI fordetermining which routing table to use. This allows customers to havetheir routing table size and speed governed by their individual addressspace, thus speeding the routing process considerably. The use ofseparate routing tables also provides an added measure of security, aspackets cannot be mis-routed due to errors or updates in routinginformation related to other customers.

In some embodiments, a router has multiple data space images paired witha single instruction space image of the routing software. Thus, forexample, as packets arrive from Customer A, the routing software usesthe data image for a routing table associated with Customer A to make arouting decision. In further embodiments, a single software image isused, but additional indices corresponding to customers are added to therouting tables. In still further embodiments, instruction execution anddata handling are processed separately. This may be accomplished by theuse of separate processors, one for instruction execution and one fordata handling.

FIG. 12 illustrates an exemplary WAN 1 having both conventional routersand IP switches incorporating aspects of the invention. In thisexemplary WAN 1, a routing element 1004 and switch 1003 are connected toCustomer Site A via frame relay switch 1001. Routing element 1007 andswitch 1006 are connected to Customer Site B via frame relay switch1009. Routing element 1012 and switch 1014 are connected to CustomerSite C via frame relay switch 1016. Routing element 1013 and switch 1015are connected to Customer Site D via frame relay switch 1017. In thisexemplary WAN 1, incoming frames 1000 from Customer Site A may beencoded with a layer 2 DLCI specifying VPN #1 as the layer 2 destinationand a layer 3 address pointing to Customer Site B. In such a case, framerelay switch 1001 switches the frames over a frame relay trunk 1002 toswitch 1003 which has layer 3 routing element 1004 associated with it.After the frame is received by switch 1003, the frame is forwarded torouter 1004 which implements short-cut routing as described above. Therouter/switch 1003, 1004 uses the layer 2 information to discriminatebetween different source customers. The layer 2 information may then bediscarded. Next, the layer 3 information in combination with a routingtable is used to make a routing decision. In this case, the routingdecision would result in a layer 3 PDU 1011 being forwarded torouter/switch 1006, 1007. The layer 3 PDU 1011 is then encapsulated witha layer 2 frame, the frame in this case being addressed to Customer SiteB. Switch 1006 then forwards the frame via a trunk 1008 to frame relayswitch 1009. At the egress port of frame relay switch 1009, the DLCI offrame relay frame 1010 is replaced with a value indicating that theframe originated from, in this case, VPN #1. The frame relay frame 1010is then delivered to the Customer B router.

As the service grows, the functionality for making the VPN routingdecisions may be migrated closer to the customer and may eventually bepresent in every switching node, as shown in FIG. 13. This can reducethe backhaul previously needed to get to the router/switch processingnodes and allow for optimal routing using all the nodes in the WAN 1and/or SPN 500. In the exemplary embodiment of FIG. 13, VPN #1 isconnected to Customer Sites A, B, C, and D. Here, every switching nodeincludes a switch 1501 and a routing element 1502. frame relay frames1500 having a DLCI directed to Customer Site B may be sent from CustomerSite A. In such a case, frames 1503 would be sent through VPN #1 viaswitching nodes 1501, 1502, and frames 1504 would be received atCustomer Site B.

In some embodiments, an ATM core network may be used for data transport,and frame relay interfaces may be used to interface with the customer.An exemplary embodiment using an ATM core network is shown in FIG. 14.In this embodiment, switch 2003 and router 2004 are connected toCustomer Site A via switch 2000 and a frame relay/ATM conversion unit2001. Switch 2019 and router 2018 are connected to Customer Site B viaswitch 2005 and frame relay/ATM conversion unit 2006. Switch 2012 androuter 2010 are connected to Customer Site C via switch 2015 and framerelay/ATM conversion unit 2014. Switch 2013 and router 2011 areconnected to Customer Site D via switch 2016 and frame relay/ATMconversion unit 2017 Assuming that Customer Site A is sending frames2020 destined for Customer Site B, incoming layer 2 frames may beencapsulated for transport into ATM cells at switch 2000 according to,for example, the Network Interworking Standard. Such encapsulation may,for example, occur in conversion unit 2001, external to ATM switch 2000.ATM cells 2002 may be sent down an ATM PVC designated for VPN #1processing. ATM cells 2002 may then be forwarded to switch 2003 androuter/switch 2004 (which may be attached to switch 2003), where the ATMcells may be reassembled to obtain the layer 3 packet information forrouting within VPN #1. Once the address information has been extractedfrom the layer 3 packet, the packet may be segmented again into ATMcells 2009 that can be transferred through the network. After being sentthrough router/switch 2018, 2019, ATM cells 2008 may be converted fromcells to frames at the external conversion unit 2006 and switch 2005.Customer Site B would then receive frame relay frames 2021. Thus, anextra segmentation and reassembly (SAR) cycle may be required when usingan ATM backbone with a core of router/switches. However, if the VPNprocessing is pushed outward to edge switches, the extra SAR cycle maybe eliminated. The extra SAR cycle may be eliminated because conversionfrom frame relay frames to ATM cells may take place in the same unitwhere VPN routing decisions are made.

Traffic management may be variously configured in the WAN 1 and/or theSPN 500. For example, from a customers viewpoint, the WAN 1 and/or SPN500 may ensure certain traffic rates for the customer.

In a network, data traffic may be sent from multiple sources to a singledestination (multi-point to point). A source is defined as the usertransmitting side of, for example, a UNI (i.e., the customer side of aUNI, which may be external to a WAN and/or to a VPN), a switch, an IPswitch, and/or a router at or near the edge of a network. A destinationis defined as the user receiving side of, for example, a UNI (i.e., thenetwork side of a UNI), a switch, an IP switch, and/or router at or nearthe edge of a network. Traffic that is offered for transmission by asource to the WAN 1 and/or SPN 500 is defined as the offered traffic.Further, a VPN source and a VPN destination are a source anddestination, respectively, which belong to a given VPN. A given UNI, ifsimultaneously sending and receiving, may simultaneously be a source anda destination. Furthermore, a given source may offer data traffic tomultiple destinations, and a given destination may receive traffic frommultiple sources.

In some embodiments of the invention, a committed delivery rate (CDR)may be assigned to each destination. The CDR is defined as the averagenumber of bits per second that the WAN 1 and/or SPN 500 is committed todeliver to a given destination, wherein the average may be calculatedover a fixed or variable time window. Although the word average will beused throughout, any other similar algorithm may be used, such as themean, the sum, or any other useful measurement and/or statisticalcalculation. If the average rate of aggregate offered traffic (i.e. thetotal offered traffic) from one or more sources to a given destinationis greater than or equal to a given destinations assigned CDR, then theWAN 1 and/or SPN 500 may guarantee to deliver traffic addressed to thedestination at an average rate equal to or greater than the CDR. If theaverage rate of aggregate offered traffic is less than the CDR, then theWAN 1 and/or SPN 500 may deliver the offered traffic to the destinationat the aggregate offered traffic rate (100% of the offered traffic). Toclarify, let the number of active sources sending traffic to aparticular destination be N. As will be described in more detail below,a source may be considered active during a given time window if thesource offers at least a threshold amount of traffic to the WAN 1 and/orSPN 500 within the given time window. Let S_(i) be the average offeredtraffic rate, or offering rate, from each source i toward a single givendestination, wherein i=[1, . . . , N]. Further, let R be the total rateat which the WAN 1 and/or SPN 500 actually delivers traffic to thedestination. Then, the WAN 1 and/or SPN 500 will provide that:${R \geq {{CDR}\quad{if}\quad{\sum\limits_{i}\quad S_{i}}} \geq {CDR}};$$R = {\sum\limits_{i}\quad{S_{i}\quad{{otherwise}.}}}$

If the aggregate offered traffic rate S_(i) does not exceed the CDR,then 100% of the offered traffic from each source i may be deliveredthrough the WAN 1 and/or SPN 500 to the destination. However, when theaggregate offered traffic rate S_(i) exceeds the CDR, the WAN 1 and/orSPN 500 may have the discretion to throttle back or reduce the deliveryrate of offered traffic from some or all of the active sources. Deliverymay be reduced by an amount such that the total rate of traffic deliveryR to a destination is at least equal to the destinations assigned CDR.In the situation where R is reduced by the network, it may be desirableto enforce fairness for each source. In other words, it may be desirableto ensure that no single source may be allowed to be greedy by obtaininga disproportionate amount of network bandwidth at the expense of othersources.

To provide for fair access to the WAN 1 and/or SPN 500, in someembodiments each source is assigned at least one destination rate share(DRS). A DRS is a rate, measured in data units per unit of time (e.g.,bits per second). A separate DRS and/or set of DRSs may be assigned toeach source and/or group of sources. Further, the DRS or DRSs for agiven source may depend upon the destination or set of destinations thatthe source may send traffic to. In other words, each source i may beassigned at least one DRS_(i) corresponding to the DRS assigned betweena source i and a given destination (or set of destinations). Thus, insome embodiments, the DRS may be different for a given source dependingupon which destination it is sending traffic to. In further embodiments,the DRS for a given source may be constant, independent of thedestination.

When a source i offers traffic at an average rate S_(i) exceeding theCDR of a particular destination, fairness may be achieved by ensuringthat each source is allowed to transmit at least its fair share of theCDR. A sources fair share of the destinations CDR is defined as thesources DRS divided by the aggregate DRS of active sources transmittingto a given destination. Thus, each active sources fair share, r_(i), ofthe CDR may be defined as the following:$r_{i} = {\frac{{DRS}_{i}}{\sum\limits_{i}\quad{DRS}_{i}}{{CDR}.}}$

The actual network transmission rate, T_(i), that the WAN 1 and/or SPN500 chooses as conforming traffic guaranteed to be delivered from eachsource to a given destination may satisfy the following:${{{when}\quad{\sum\limits_{i}\quad S_{i}}} \geq {CDR}},{T_{i} \geq {{\min\left( {r_{i},S_{i}} \right)}.}}$

Thus, in these embodiments the WAN 1 and/or SPN 500 may enforce fairnessby reducing one or more sources actual network transmission rate T_(i)at most from S_(i) to r_(i), ensuring that each source obtains its fairshare of the CDR. In some embodiments, to achieve a rate of at leastCDR, the WAN and/or SPN 500 may at its discretion transmit traffic froma given active source or sources at a rate greater than r_(i). In fact,the WAN 1 and/or SPN 500 may at its discretion transmit data from asource i at any rate between and including the fair share rate r_(i) andthe full offered rate S_(i).

If S_(i) is greater than T_(i), a source may be considered by the WAN 1and/or SPN 500 to be a non-conforming source. Conformance of a sourcemay be calculated using a standard leaky bucket algorithm with variabledrain rate. Thus, the conforming depth of a bucket would be DRS_(i)*W.In other words, the maximum number of bits that will be sent to thenetwork within a given time window of length W is equal to DRS_(i)*W.During a given time window of length W, the drain rate of the bucket isequal to T_(i) which is calculated during previous time windows. Thus,data packets inserted above the conforming bucket depth may be labeledas non-conforming. In other words, for a given time window, data packetsin excess of the total DRS_(i)*W number of bits may be labeled asnon-conforming data packets. In such a situation, some or all of thesource data packets equal to the difference between S_(i) and T_(i) maybe labeled as non-conforming data packets, and some or all of thenon-conforming data packets may be dropped.

This does not mean that data cannot be of a bursty or rate-variantnature. Although exemplary embodiments have been described as operatingusing average rates, real-time rates may vary within any given timewindow of length W. Thus, a certain amount of burstiness of data isallowable. This maximum burst size is the maximum number of bits thatthe WAN 1 and/or SPN 500 guarantees to transfer during a time window W.

In further embodiments of the invention, the WAN 1 and/or SPN 500 mayprovide forward congestion notification to a destination. For example,the WAN 1 and/or SPN 500 may provide a layer 2 binary indication thatthe CDR is being exceeded by using the frame relay forward explicitcongestion notification (FECN) bit and/or a layer 3 message thatindicates a non-conforming source and optionally contains rateinformation for that source (e.g. the actual transmitted rate T_(i)and/or the excess rate S_(i)-T_(i)). Furthermore, in some embodiments,multiple non-conforming sources might be listed, even within a singlemessage. In these forward congestion notification embodiments,conformance may be measured at the network side of a destination. Insome embodiments, a forward congestion notification may be provided to agiven destination when the offering rate S_(i) of an active sourceoffering to send traffic to the destination exceeds the actual networktransmission rate T_(i) for the source.

Non-conforming packets that cannot be transmitted on the egress port ofa source may be dropped with or without any indication to the source ordestination. To measure conformance of a source, the amount of excessbandwidth available to the sources for transmission to the destinationshould be determined. To calculate the excess bandwidth, let W_(j) bethe j^(th) time window. The excess bandwidth above the fair sharebandwidth may be computed as${E = {{CDR} - {\sum\limits_{i}\quad{\min\left( {r_{i},S_{i}} \right)}} - {MB}}},$wherein M is defined as the number of possible sources from which adestination may receive traffic, and wherein B is defined as apredetermined reference rate. The introduction of reference rate Beffectively reserves network bandwidth for an inactive source, thusensuring that a previously inactive source that becomes active can sendat least some traffic through the network during time period W_(j).Specifically, the WAN 1 and/or SPN 500 may ensure that each sourcesT_(i) is guaranteed to be at least a minimum reference rate B. In thissituation, a source is considered active during W_(j) if more thanB*W_(j) units of data (e.g., bits) are received during W_(j). It isdesirable to define B to be relatively small as compared with S_(i) soas to retain as much excess bandwidth as possible, yet still largeenough to ensure network availability to a non-active source(non-sending source with respect to a given destination) that may laterbecome active with respect to a given destination. In some embodiments,B may be a predetermined rate. In further embodiments, B may vary withtime, with the number of inactive sources, with the number of activesources, and/or with the total number of sources. In still furtherembodiments, B for a source may depend upon a priority classificationassigned to the source. In still further embodiments, when a previouslyinactive source becomes active, the priority assigned to the source maydepend upon the content of the data (e.g., data payload, DLCI, and/oraddress) offered to be sent. Thus, B may not be the same for eachsource.

Once the excess bandwidth is determined, the maximum conforming actualnetwork transmission rates, T_(i), may be calculated. To accomplishthis, T_(i) for each source may first be set by default to min(r_(i),S_(i)). Then the excess bandwidth, E, may be distributed among some orall of the sources that are actively transmitting to the givendestination, thus adjusting or raising T_(i) for these sources. In someembodiments, the excess bandwidth may be uniformly distributed amongsome or all of the active sources. In further embodiments, the excessbandwidth may be distributed among these sources according to sourcepriority, data priority, and/or DLCI.

In further embodiments, the WAN 1 and/or SPN 500 may provide backwardcongestion notification to a non-conforming source. Such notificationmay be in the form of a layer 2 and/or a layer 3 message indicating adestination(s) for which the non-conforming source is exceeding T_(i)and/or rate information for the non-conforming source (e.g. the actualtransmitted rate T_(i) and/or the excess rate S_(i)-T_(i)). However, alayer 2 notification by itself may not be preferable, since a sourcereceiving only a layer 2 notification may not be able to distinguishbetween destinations to which the source is conforming and those forwhich it is not conforming. In some embodiments, a backward congestionnotification may be provided to a given active source when the offeringrate S_(i) of the source exceeds the actual network transmission rateT_(i) for the source. In further embodiments, a user at a non-conformingsource may be notified of congestion information, the assigned CDR,DRS_(i), r_(i), and/or T_(i). In still further embodiments, it may be upto a user to decide how to act upon a congestion notification. In evenfurther embodiments, a source may reduce its offering rate S_(i) inresponse to receiving a backward congestion notification.

In these backward congestion notification embodiments, conformance maybe implemented at the network side of the source UNI. In suchembodiments, feedback concerning the destination delivery rate may berequired from the destination. The feedback may also contain informationregarding the rate share of the active sources at the destination and/orthe CDR divided by the aggregate rate.

While exemplary systems and methods embodying the present invention areshown by way of example, it will be understood, of course, that theinvention is not limited to these embodiments. Modifications may be madeby those skilled in the art, particularly in light of the foregoingteachings. For example, each of the elements of the aforementionedembodiments may be utilized alone or in combination with elements of theother embodiments. Additionally, although a meshed network is shown inthe examples, the inventions defined by the appended claims is notnecessarily so limited. Further, the IP switch may convert from anyhigher level IP like protocol to any fast-packet like protocol and isnot necessarily limited to the ATM/IP example provided above.Furthermore, examples of steps that may be performed in theimplementation of various aspects of the invention are described inconjunction with the example of a physical embodiment as illustrated inFIG. 5. However, steps in implementing the method of the invention arenot limited thereto. Additionally, although the examples have beenderived using the IP protocol for layer three, it will be apparent tothose skilled in the art that any version of IP or IPX could be used asthe layer three routeable protocol. Furthermore, it will be understoodthat while some examples of implementations are discussed aboveregarding IP and ATM protocols, the invention is not intended to belimited solely thereto, and other protocols that are compatible withaspects of the invention may be used as well.

1. A method comprising the steps of: receiving frame relay data packetsinto a fast packet network, and switching said frame relay data packetswithin the fast packet network responsive to a dynamically computed datalink connection identifier (DLCI), each DLCI corresponding to aplurality of destinations.
 2. The method of claim 2, wherein theplurality of destinations comprises a virtual private network.
 3. Themethod of claim 2, wherein each frame relay data packet comprises userdata in a user data field.
 4. The method of claim 3, further comprisingthe step of routing said frame relay data packets within the virtualprivate network responsive to the user data.
 5. The method of claim 4,wherein the user data further comprises one of voice data, video data,and multicast data.
 6. The method of claim 5, wherein the user datacomprises and IP address.
 7. The method of claim 1, wherein said dynamiccomputation comprises basing the data link connection identifier (DLCI)on interactive application information.
 8. The method of claim 7,wherein said interactive application information corresponds to a telnetapplication.
 9. The method of claim 8, wherein said interactiveapplication information corresponds to a file transfer protocol (FTP)application.
 10. The method of claim 8, wherein said interactiveapplication information corresponds to a network based application. 11.The method of claim 1, wherein said dynamic computation comprises basingthe data link connection identifier (DLCI) on a layer 3 network address.12. The method of claim 11, wherein said layer 3 network addresscomprises an internal company address.
 13. The method of claim 12,wherein said internal company address is located within a virtualprivate network.
 14. A method in a fast packet network comprising thesteps of: receiving a fast packet; comparing an address of the fastpacket with a layer 3 internet protocol address contained within thefast packet; and determining whether the address is consistent with thelayer 3 internet protocol address.
 15. The method of claim 14 whereinthe step of determining includes examination of a sending address or adestination address.
 16. The method of claims 14 further including thestep of discarding packets responsive to an inconsistency beingdetected.
 17. The method of claim 14 wherein the fast packet is anasynchronous transfer mode packet.
 18. An apparatus comprising: meansfor receiving into a fast packet network frame relay data packets, saidframe relay data packets having user data in a user data field, whereinsaid user data comprises service category data; means for switching saidframe relay packets within the fast packet network responsive to theuser data; means for discriminating between a plurality of servicecategories based on the user data; and means for routing over a virtualprivate network responsive to at least one of the service categories.19. The apparatus of claim 18 further including means for routing overthe virtual private network, the virtual private network comprisingtrading partners responsive to at least one of the service categories.20. The apparatus of claim 18 further including means for routing over aclosed user group responsive to at least one of the service categories.